Summary

docs #2011 corrected the vNext CLI reference and explicitly deferred the versioned snapshots:

Not propagated to versioned_docs/: --output arrived per command across different releases (status in v1.11.x, most others after v1.11.2), so the versioned snapshots diverge command-by-command and need their own pass rather than a copy of this one.

This is that pass, done command-by-command against the release tags. The result: v2.0.1 and v2.1.2 expose the identical CLI surface — same seven global flags, same ten commands with -o/--output, same upgrade/version/refresh/trace flags — so both snapshots carry the same wrong claims and both are fixed here.

What the 2.0.x / 2.1.x docs said vs. what the released binaries do:

Verification

Read the clap derive attributes at each tag — git show <tag>:bin/spice/src/....

Global flags — bin/spice/src/main.rs, struct Cli: seven global = true args at both v2.0.1 and v2.1.2, with the documented details identical at both: alias = "programmatic" on --machine, env = "SPICE_API_KEY" on --api-key, requires = "cloud" on --cloud-region, DEFAULT_CLOUD_REGION = "us-east-1", default_value = "http://127.0.0.1:8090" on --http-endpoint.

-o/--output — enumerated by grepping short = 'o' across bin/spice/src/commands/** at each tag. Identical sets: catalogs, chat, datasets, models, pods, refresh, sql, status, trace, version (plus the already-documented query/mod.rs, search.rs, login/mod.rs, and the undocumented acceleration, workers, cloud). OutputFormat { Table (default), Json }.

upgrade — commands/upgrade.rs at both tags: #[arg(name = "target_version")] version: Option<String>, #[arg(short, long)] force, the !version.starts_with('v') rejection, and about = "Upgrades the Spice CLI and runtime to the latest or specified version".

Per-command flags — version.rs #[arg(long)] cli_only; refresh.rs refresh_jitter_max; trace.rs #[arg(long, default_missing_value = "80")] truncate: Option<usize>. All present at both tags.

Scoped per version — not a flat copy

• tool_use::<tool> trace task names → 2.1.x only. The vNext trace.md paragraph documents both the bare tool_use::<tool> and the tool_use::<server>/<tool> forms. At v2.1.2 both exist (crates/runtime-tools/src/mcp/server.rs:169 and mcp/tool.rs:93). At v2.0.1 only tool_use::<server>/<tool> is emitted (crates/runtime/src/tools/mcp/tool.rs:93; that release's tools/mcp/server.rs records no task span at all), so 2.0.x gets the flag rows without that paragraph.
• version-1.11.x and older are deliberately untouched. v1.11.6 declares a different, smaller set — 5 global = true args, not 7 — so a copy of this table would be wrong there. Those snapshots need their own verified pass; noted rather than guessed.
• version-2.0.x was byte-identical to the pre-change version-2.1.x for all 12 pages, so the two snapshots genuinely shared one set of claims rather than being independently stale.

Grep coverage

$ grep -rln -- "--output" website/versioned_docs/version-2.1.x/cli/reference/   # before
search.md  login.md  query.md

The CLI reference pages are the only place these flags are enumerated: grep -rln 'cli-only\|refresh-jitter-max\|target_version' returns no other page type.

Test plan

• cd website && npm run build passes (onBrokenLinks/onBrokenAnchors/onInlineTags all throw) — 3750 documents, Generated static files in "build". The new refresh.md links (../../reference/duration, ../../features/data-acceleration/data-refresh#refresh-jitter) were confirmed to resolve in both snapshots before building.
• Versioned-docs propagation checked and scoped per release (above)
• Files updated: 24 — 12 under version-2.1.x/cli/reference/, 12 under version-2.0.x/cli/reference/ (matches the diff)